fix: Fix logging for Lambda functions in the privatelink-access pattern
#1800
+13
−12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vchintal
temporarily deployed
to
EKS Blueprints Test
GitHub Actions
Inactive
vchintal
changed the title
privatelink-access patternprivatelink-access pattern
bryantbiggs
approved these changes
Oct 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes the broken/non-functional logging in the Lambda functions of the
privatelink-accesspattern.Motivation and Context
privatelink-accesspattern doesn't work #1798How was this change tested?
pre-commit run -awith this PRAdditional Notes
None